Method for detecting rogue devices operating in wireless and wired computer network environments

ABSTRACT

A management of wireless and wired computer network environments in which rogue and other devices that may affect the performance and/or security of the wireless computer network can be detected. Specifically, the present invention discloses a method and system of detecting all interfaces, Media Access Control (MAC) addresses and radio MAC addresses (BSSIDs) affiliated with a rogue device and compiling this information into a database. As a result, the present invention reduces the number of alerts that one rogue device can generate and increases the accuracy and speed of locating the rogue device within a network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 11/869,624, entitled METHODS, APPARATUSES AND SYSTEMSFACILITATING MANAGEMENT OF AIRSPACE IN WIRELESS COMPUTER NETWORKENVIRONMENTS, which is a divisional of U.S. Pat. No. 7,295,524, entitledMETHODS, APPARATUSES AND SYSTEMS FACILITATING MANAGEMENT OF AIRSPACE INWIRELESS COMPUTER NETWORK ENVIRONMENTS, filed Feb. 18, 2003, and issuingon Nov. 13, 2007. The contents of both U.S. patent application Ser. No.11/869,624 and U.S. Pat. No. 7,295,524 are incorporated herein byreference into the present application.

FIELD OF THE INVENTION

The present invention relates to wireless and wired computer networksand, more particularly, to methods, apparatuses and systems for themanagement of wireless and wired computer network environments, in whichrogue and other devices that may affect the performance and/or securityof the wireless computer network can be detected.

BACKGROUND OF THE INVENTION

In 1997, the Institute of Electrical and Electronics Engineers (IEEE)approved 802.11 the first internationally sanctioned wireless local areanetwork (WLAN) standard. The IEEE 802.11 standard establishesspecifications for the parameters of both the physical (PHY) and mediaaccess control (MAC) layers of the network. The IEEE ratified theoriginal 802.11 standards as the standard for WLANs. The initialstandard provided 1 Mbps and 2 Mbps transmission rates. This rate oftransmission was not sufficient for most general business applicationsand consequently the rate of adoption was slow.

Recognizing the need for faster transmission speeds, the IEEE ratifiedthe 802.11b standard to allow for transmission speeds of up to 11 Mbps.The new standard aligns wireless connectivity on comparable levels towired Ethernet LANs. The range for WLANs depends largely on the mediumby which the radio waves are transmitted and the strength of thetransmitting antenna. Ranges in open air are much longer than in areascomprising several walls between antennas. Depending on the type ofradio antenna (omni-directional, bi-directional, etc.) and transmitterstrength, optimal distances can vary from 200 feet to 10 miles. Fallbackspeeds of 5.5, 2, and 1 Mbps occur when optimal distances fortransmission are exceeded.

The first 802.11 standard proposed three implementations for thePhysical Layer (PHY): Infrared (IR) Pulses Position Modulation, RFSignaling using Frequency Hopping Spread Spectrum (FHSS), and DirectSequence Spread Spectrum (DSSS). Two working groups were established toexplore alternate implementations of the 802.11 standard. Working GroupA explored the 5.0 GHz band, while Working Group B focused on the 2.4GHz band. Wireless communications take place within an area known as theBasic Service Area defined by the propagation characteristics of thewireless medium. A wireless node communicates via a Basic Service Set(BSS) within a basic service area. There are two basic service sets:independent and infrastructure. The independent service set allowswireless stations to operate in a peer-to-peer or ad hoc mode. In the adhoc network, computers are brought together to form a network “on thefly.” There is no structure to the network; there are no fixed points;and usually every node is able to communicate with every other node.Although it seems that order would be difficult to maintain in this typeof network, algorithms such as the spokesman election algorithm (SEA)have been designed to select one wireless node as the base station(master) of the network with the others being slaves. The infrastructureservice set is the more common approach involving access points (APs)that allow for and control access to the wireless network. An accesspoint usually contains a transceiver, a wired network interface (e.g.,802.3) and software for data processing. If service areas of accesspoints overlap, handoffs of wireless clients between access points canoccur.

Wireless local area networks (WLANs), need their air space to beconsistently mapped in order to maintain optimum speed and reliability.In an Ethernet LAN (IEEE 802.3), the Carrier Sense Multiple Access withCollision Detection (CSMA/CD) protocol establishes how simultaneoustransmissions (packet collisions) are handled. In a WLAN, collisiondetection in this manner is not possible due to what is known as the“near/far” problem: to detect a collision, a station must be able totransmit and listen at the same time. To account for this difference,the 802.11 protocol uses a slightly different protocol known as CarrierSense Multiple Access with Collision Avoidance (CSMA/CA) or theDistributed Coordination Function (DCF). CSMA/CA attempts to avoidpacket collisions by using explicit packet acknowledgement (ACK), whichmeans that an ACK packet is sent by the receiving station to confirmthat a packet arrived intact. CSMA/CA works by having the transmittingwireless station sense the air. If there is no activity detected, thetransmitting wireless station will wait an additional random period oftime. If there still is no activity, the wireless station transmits thedata. If the packet is received intact, the receiving station will sendand ACK frame that, once received by the original sender, completes thetransmission. If the ACK command is not received in a specified randomperiod of time, the data packet will be resent, with the assumption thatthe original packet experienced a collision. CSMA/CA will also handleother interference and radio-wave related problems effectively, butcreates considerable overhead.

Given the collision avoidance mechanisms employed in 802.11-compliantwireless networks, management and monitoring of the wireless networkairspace is critical to the performance of the wireless networkenvironment (for example, to ensure that wireless access points do notinterfere with one another). The administrative or managementfunctionality associated with WLAN networks, however, generally lacks areliable and accurate means of collecting, storing, and relatingairspace data. Hand-held scanners, AP startup scans, or full-timescanning devices are the current methods of obtaining WLAN air spacedata. However, these methods are inherently flawed or not costeffective. Accordingly, most WLANs do not perform at optimum speed dueto overlapping channel interference and rogue access points (i.e.,access points installed without authorization and/or knowledge of anetwork administrator).

In light of the foregoing, there exists a need in the art for methods,apparatuses and systems that allow for efficient mapping of the airspace associated with wireless networks. A need further exists formethods, apparatuses and systems that facilitate detection of rogue orunauthorized wireless access points.

SUMMARY OF THE INVENTION

The present invention provides methods, apparatuses and systemsfacilitating the management of wireless computer and wired computernetwork environments and the detection of rogue and other devices thatmay affect the performance and/or security of the wireless computernetwork. The present invention enables accurate and cost effective WLANair space mapping. In one embodiment, the present invention allows anyconforming access point the ability to routinely scan its airspace,collect data on all operating frequencies and report this informationback to a management platform. Management and reporting functionalitydescribed herein uses a standards-based vehicle, such as Simple NetworkManagement Protocol (SNMP). The present invention allows for detectionof all wireless traffic within or affecting an enterprise's computernetwork environment, picking up all active access points (ad hoc orinfrastructure) and all wireless clients data regardless of SSID,channel, or security settings. The management platform, according to anembodiment of the present invention, analyzes information received fromthe access points under management to detect and report the state of thecomputer network environment. The present invention facilitatesisolation of rogue wireless devices affecting the computer networkenvironment and effective decision-making as to management of thedetected device. The present invention also allows networkadministrators to optimize the configuration of the wireless networkenvironment for performance and security.

The present invention also discloses management of wireless and wiredcomputer network environments in which rogue and other devices that mayaffect the performance and/or security of the wireless computer networkcan be detected. Specifically, the present invention discloses a methodand system of detecting all interfaces, Media Access Control (MAC)addresses and radio MAC addresses (BSSIDs) affiliated with a roguedevice and compiling this information into a database. As a result, thepresent invention reduces the number of alerts that one rogue device cangenerate and increases the accuracy and speed of locating the roguedevice within a network.

In one aspect, the present invention is directed to a method ofidentifying Media Access Control addresses of rogue devices operating ina hybrid network, the method comprising: identifying Basic Service SetIdentifiers for devices operating on a wireless network; creating arogue discovery event for at least one of the Basic Service SetIdentifiers of a device not authorized to operate in the hybrid network;determining a root Basic Service Set Identifier from the rogue discoveryevent; assigning the root Basic Service Set Identifier to a rogue devicerecord; searching the hybrid network for wired devices associated withthe root Basic Service Set Identifier and determining correspondingMedia Access Control addresses for the located wired devices; andcomparing the Media Access Control addresses with a plurality of octetsof the root Basic Service Set Identifier in the rogue device record.

In another aspect of the present invention, the method further comprisesassigning a score to the rogue discovery event based on security risk.

In another aspect of the present invention, the method further comprisescomparing the identified Basic Service Set Identifiers with a list ofBasic Service Set Identifiers of devices controlled by a managementplatform to determine whether the corresponding device is authorized tooperate in the hybrid network.

In another aspect of the present invention, the method further comprisesmapping a radio frequency environment from the rogue discovery event.

In another aspect of the present invention, the method further compriseslocating each of the devices operating on the wireless network via atriangulation method.

In another aspect of the present invention, the method further comprisesdetermining channel information from the rogue discovery event.

In another aspect of the present invention, the method further comprisesdetermining security information from the rogue discovery event.

In another aspect of the present invention, the method further comprisesdetermining signal strength from the rogue discovery event.

In another aspect of the present invention, the method further comprisesidentifying a device having the closest address when more than one MediaAccess Control addresses match the root Basic Service Set Identifier inthe rogue device record.

In another aspect of the present invention, the method further comprisesanalyzing all rogue discovery events for the at least one of the BasicService Set Identifiers to determine a virtual Basic Service SetIdentifier.

In another aspect of the present invention, the method further comprisescreating a rogue interface record for the virtual Basic Service SetIdentifier.

In another aspect of the present invention, the method further comprisescreating a rogue interface record for the root Basic Service SetIdentifier.

In another aspect of the present invention, the comparing step furthercomprises comparing the Media Access Control addresses with a first fiveoctets of the root Basic Service Set Identifier in the rogue devicerecord.

In another aspect of the present invention, the method further comprisescreating additional rogue interface records for each of the Media AccessControl addresses that correspond to the first five octets of the rootBasic Service Set Identifier.

In another aspect of the present invention, the method further comprisessearching the additional rogue interface records for the Media AccessControl addresses having corresponding Internet Protocol addresses.

In another aspect of the present invention, the method further comprisesquerying at least one of the Internet Protocol addresses to determine anoperating system of the corresponding rogue device.

In another aspect of the present invention, the searching step furthercomprises reading bridge forwarding tables on a switch to find the wireddevices.

In another aspect of the present invention, the method further comprisesthe searching step further comprises reading address resolution protocoltables of a router to find the wired devices.

In another aspect, the present invention is further directed to a systemfor performing a computer-based method of identifying Media AccessControl addresses of rogue devices operating in a hybrid network,comprising a computer having a memory and a processor; and acomputer-readable medium configured to generate software code, which,when said code is loaded into the memory and run by the processor,causes the processor to perform the steps of identifying Basic ServiceSet Identifiers for devices operating on a wireless network; creating arogue discovery event for at least one of the Basic Service SetIdentifiers of a device not authorized to operate in the hybrid network;determining a root Basic Service Set Identifier from the rogue discoveryevent; assigning the root Basic Service Set Identifier to a rogue devicerecord; searching the hybrid network for wired devices associated withthe root Basic Service Set Identifier and determining correspondingMedia Access Control addresses for the located wired devices; andcomparing the Media Access Control addresses with a plurality of octetsof the root Basic Service Set Identifier in the rogue device record.

In another aspect, the present invention is further directed to a systemfor performing a computer-based method of identifying Media AccessControl addresses of rogue devices operating in a hybrid network,comprising a computer having a memory and a processor; and acomputer-readable medium configured to generate software code, which,when said code is loaded into the memory and run by the processor,causes the processor to perform the steps of identifying Basic ServiceSet Identifiers for devices operating on a wireless network; creating arogue discovery event for at least one of the Basic Service SetIdentifiers of a device not authorized to operate in the hybrid network;determining a root Basic Service Set Identifier from the rogue discoveryevent; assigning the root Basic Service Set Identifier to a rogue devicerecord; assigning a score to the rogue discovery event based on securityrisk; searching the rogue discovery event to determine a virtual BasicService Set Identifier; searching the hybrid network for wired devicesassociated with the root Basic Service Set Identifier and determiningcorresponding Media Access Control addresses for the located wireddevices; comparing the Media Access Control addresses with a first fiveoctet of the root Basic Service Set Identifier in the rogue devicerecord; creating a rogue interface record for the virtual Basic ServiceSet Identifier, the root Basic Service Set Identifier and for MediaAccess Control addresses that correspond to the first five octets of theroot Basic Service Set Identifier; searching the additional rogueinterface records for the Media Access Control addresses having InternetProtocol addresses; and displaying a location of at least one roguedevice.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a wireless computer network environmentaccording to an embodiment of the present invention;

FIG. 2 shows a user interface providing a detailed list of managedwireless access points;

FIG. 3 sets forth a user interface providing detailed informationassociated with a given wireless access point;

FIG. 4 provides a user interface that allows a user to initiate a scanat a given access point for rogue devices operating within its airspace;

FIG. 5 illustrates a user interface allowing a network administrator toinitiate a scan for rogue access points for a group of wireless accesspoints;

FIG. 6 is a flow chart diagram showing a method, according to oneembodiment, for scanning at an access point for rogue devices;

FIG. 7A illustrates the layout of management frames or packets in 802.11networks and the mapping of information in the frames;

FIG. 7B provides the layout of data frames or packets in 802.11networks;

FIG. 8 illustrates a memory buffer constructed during a scan for roguedevices and a table illustrating the elements of SNMP traps summarizingthe data in the memory buffer;

FIG. 9 is a flow chart illustrating a method OF processing SNMP trapstransmitted by scanning access points;

FIG. 10 illustrates a user interface showing a list of detected rogueaccess points;

FIG. 11 illustrates a user interface showing a detail view of a givenrogue access point detected during a scan;

FIGS. 12 a and 12 b illustrate a flow chart for a method of scanning forrogue devices, gathering data, analyzing the data gathered, and buildinga master device record;

FIG. 13 illustrates an example of data retrieved from the device and thedatabase record according to an exemplary embodiment;

FIG. 14 illustrates a screen display showing location of devices inaccordance with an exemplary embodiment; and

FIG. 15 illustrates a screen display showing a list of all interfaces ona rogue device in accordance with an exemplary embodiment.

DESCRIPTION OF PREFERRED EMBODIMENT(S) I. Computer Network Environment

FIG. 1 illustrates a computer network environment including anembodiment of the present invention. As FIG. 1 illustrates, the presentinvention, in one embodiment, operates in a computer network environmentincluding a local area network (LAN) 20 interconnecting a plurality ofhosts or other end systems, such as servers, network computers, etc.,airspace management platform 56, and at least one wireless access point52. Other computer network environments are possible. For example, whileFIG. 1 illustrates that airspace management platform 56 and the at leastone wireless access point 52 are connected via a LAN 20, embodiments ofthe present invention can be deployed across a wide area network, suchas the Internet, to allow a network administrator to remotely manage oneto a plurality of network access points 52 from distant locations.

Wireless access points 52 can act as a hub to route data betweenwireless client devices 60 within its coverage area, and/or bridgenetwork traffic between a computer network 20 and one or more wirelessclient devices 60. A Basis Service Set (BSS) 64 refers to the wirelessnetwork implemented by a given wireless access point 52 that manages andbridges wireless communications for all wireless client devices 60within its operating range (Basic Service Area (BSA) and operating onthe same frequency channel (see FIG. 1). In 802.11-compliant wirelessnetworks, a Service Set Identifier (SSID), a unique, 32-characteridentifier attached to the header of data packets transmitted over aWLAN, acts as a form of password or token when wireless client devices60 attempt to connect to a Basic Service Set. The SSID differentiatesone WLAN from another in that all wireless client devices 60 attemptingto connect to a specific WLAN must use the same SSID. An ExtendedService Set (ESS) 66 refers to two or more Basic Service Sets, havingthe same SSID, that are interconnected by a Distribution System (DS)(such as an Ethernet LAN 20), which provides a set of services enablingthe transport of data between BSSs.

Wireless access point 52 is operative to dynamically recognize newusers/wireless client devices 60 and wirelessly communicate with one toa plurality of wireless client devices 60. Wireless access point 52includes a radio frequency transmitter/receiver unit or an infraredtransmitter receiver unit, or both. However, any suitable means ofwireless communication can be used. Wireless access point 52 can operatein connection with any wireless communications protocol, including802.11a and 802.11b, as well as Bluetooth. Wireless access point 52 isfurther operative to allow access to resources operably connected tocomputer network 20. In one embodiment, wireless access point 52 isoperative to convert all wireless traffic to Ethernet (or other LAN ornetwork protocol) and route it to appropriate systems connected tocomputer network 20. Of course, the specific or optimal networkprotocols used in connection with the present invention may vary withthe protocols implemented on LAN 20. In one embodiment, wireless accesspoint 52 routes all wireless traffic from client devices 60 to a singlelocation in the computer network embodiment (in one embodiment, a secureaccess server that authenticates users at client devices and controlsaccess to resources connected to computer network 20). Co-pending andcommonly owned U.S. application Ser. No. 10/271,106 filed Oct. 15, 2002and entitled “Secure Wireless Network Access Points,” (incorporated byreference herein), discloses methods and systems directed to securingwireless network access points. In one embodiment, wireless access point52 includes tunneling functionality establishing and maintaining avirtual communications tunnel between access point 52 and the secureaccess server as disclosed in U.S. application Ser. No. 10/271,106,above. However, as one skilled in the art will recognize, the presentinvention can be applied in connection with a variety of secure andnon-secure wireless network access point configurations. In oneembodiment, at least one wireless network access point 52 includesscanning agent functionality operative to monitor its surroundingairspace for wireless traffic relative to at least one frequencychannel, gather data characterizing detected wireless traffic, andtransmit the data to airspace management platform 56 for processing andpresentation to a network administrator. In WLAN environments employing802.11 protocols, the wireless access point(s) 52 are equipped with802.11-compliant WLAN network interface cards which support RadioFrequency (RF) monitoring mode, as well as the proper device drivers. Inone embodiment, the wireless access point 52 includes an SNMP ManagementInformation Base (MIB) for standards-based delivery of the scan datafrom the access point to the airspace management platform. In oneembodiment, the scanning agent is a software daemon that is invoked whenan SNMP SET request is received; the scanning agent operates to scan itsairspace and transmit SNMP traps or populate its MIB characterizing thedevices detected within its coverage area and then allows the wirelessaccess point 52 to resume normal operation.

As discussed in more detail below, airspace management platform 56facilitates management and overview of the wireless access point(s) 52operably connected to computer network 20 and, in connection with one ormore suitable wireless access point(s) 52, is operative to monitor thewireless network airspace associated with an administrative domain forwireless client devices and/or network access points, includingknown/authorized and/or rogue devices and access points. As discussed inmore detail below, airspace management platform 56, in one embodiment,allows network administrators to schedule wireless access point (s) 52to perform regular or intermittent scans, as well as start scanson-demand. Airspace management platform 56 is further operative toreceive data from the network access point(s) 52, interpret the receiveddata, and present it in a variety of interfaces to a networkadministrator to allow for intelligent, well-informed decision-making asto the computer network domain. In one embodiment, airspace managementplatform 56 is a Web-based application executed on a server or othercomputing device operably connected to computer network 20, andaccessible via a client computer including suitable browsing software,such as Microsoft® Internet Explorer®, or Netscape® Navigator browsers.In another embodiment, airspace management platform 56 may reside on adesktop computer associated with a network administrator.

II. Operation

A. Registration and Management of Access Points

Using the airspace management platform 56, a network administratorregisters at least one wireless access point 52 by entering ordiscovering information unique to the access point, such as BSSID orWireless MAC address, LAN MAC address, and LAN IP address. As discussedbelow, BSSID or Wireless MAC address, LAN MAC address, and IP addressare used as indexes in tables or other data structures that storeinformation about each access point. Wireless access point(s) 52 thatare registered with the airspace management platform 56 can then be usedto scan for rogue access points and client devices, as discussed below.After registration, access points are authorized or brought undermanagement of airspace management platform 56. The airspace managementplatform 56 can monitor the registered wireless access point(s) overcomputer network 20 via Simple Network Management Protocol (SNMP) readcommunity string, and configure the wireless access point(s) 52 via SNMPread-write community string.

In one embodiment, airspace management platform 56 discovers thefunctionality and other parameters associated with registered wirelessaccess points and populates a database (such as the tables, below) thatincludes information on each registered wireless access point 52.Airspace management platform 56, in one embodiment, supports a varietyof Layer 2 discovery protocols such as CDP (Cisco Discovery Protocol),CDP (Cabletron Discovery Protocol, OSUNMS, and WNMS. Layer 2 discoverymethods are suitable when airspace management platform 56 is on the samephysical network as the access points 52. Higher layer discoverymethods, such as SNMP and HTTP subnet scanning, are valuable fordiscovering wireless access points 52 on networks in which airspacemanagement platform 56 is not physically located.

A.1. Access Point Master Table

As discussed above, airspace management platform 56 maintains a databasestoring information relating to the wireless access point(s) within theairspace associated with the computer network domain. In one embodiment,the database is a relational database comprising a plurality of tables,including a Master_AP table, an AP_Capabilities table, as well as othertables set forth below. In one embodiment, airspace management platform56 creates a record in an AP_Master table including information gatheredduring the registration and discovery processes. The AP_Master table, inone embodiment, includes the following fields: 1) AP_Name (a userdefinable field of 32 characters), 2) Wireless Interface MAC address(Media Access Control, a 48-bit address generally displayed as 12hexadecimal digits), 3) LAN Interface MAC Address, 4) LAN IP, 5) ServiceSet Identifier, 6) Type (i.e., Manufacturer and Product Name), 7)Firmware Version, 8) Channel, 9) Uptime, 10) Positional Parameters(e.g., Latitude and Longitude), and 11) a RogueScanFlag (indicatingwhether the wireless access point supports rogue access point scanning).Other fields can include: 12) Group Name (a user definable fieldindicating a grouping of access points for administrative purposes, seebelow), 13) status [up/down], 14) number of users, and 15) bandwidth.

The AP_Master table has several indexes which are employed in rogueaccess point detection. In one embodiment, the primary keys for theAP_Master table are: AP_Name, LAN Interface MAC Address (LAN_MAC), andWireless Interface MAC Address (WLAN_MAC). Another field of importanceto rogue access point detection in the AP_Master table is theRogueScanFlag. This flag is a Yes/No data type, where “Yes” indicatesthat the access point supports rogue AP scanning, and “No” indicatesthat the access point does not support rogue AP scanning. As discussedabove, the database maintained by airspace management platform 56contains an AP_Capabilities table relating AP manufacturer, model, andability to support rogue scanning. When access points are registered andinserted into the AP_Master table the AP_Capabilities table is queriedby manufacturer and model name to correctly set the RogueScanFlag in theAP_Master table.

As FIG. 2 illustrates, airspace management platform 56 provides anoverview of the wireless access points, displaying, in one embodiment, asubset of the values or fields of the APMaster table to the networkadministrator. As FIG. 3 shows, airspace management platform 56 alsoallows the user to click on a particular access point in the interfacedepicted in FIG. 2 to see a detailed view of a desired wireless accesspoint, such as the users currently associated with a wireless accesspoint 52.

A.2. Administrative Groups

Once registered, wireless access point(s) 52 are ready for inclusion inscans for rogue access points. As discussed above, airspace managementplatform 56 allows a network administrator to define two or more managedwireless access point(s) into groups for administrative purposes, suchas applying configuration changes and the scheduling of rogue accesspoint scans. Airspace management platform 56 allows a networkadministrator to initiate a scan at the access point level (see FIG. 4,button 91), or at the group level (see FIG. 5). In one embodiment, a“group” encompasses access points sharing similar security and radiocharacteristics. For example, in the WLAN set forth in FIG. 1, wirelessaccess points named “Sales1” and “Sales2” are associated with a groupdefined by a network administrator. These wireless access points sharethe same SSID and security settings geared for the Sales department or“Sales Group” as defined in airspace management platform 56.Accordingly, in this example, the employees or other users associatedwith the sales department would configure their wireless client devices(WLAN network interface cards) to associate with access points having anSSID set to “Sales.” In another embodiment, a group is arbitrarilydefined by an administrator according to any desired criteria, such aslocation, department, etc. Groups can be used to simplify administrationof a wireless LAN functionality, because configuration changes for agroup can be entered once and automatically applied to all wirelessaccess points associated with the group. In addition, groups provide avery efficient way of viewing or monitoring the wireless network.Executing a rogue AP scan by group enables a WLAN administrator totrigger scanning on all wireless access points in the) group that havescanning capability with minimal effort.

A.3. Scheduling of AP Scans

As FIG. 5 illustrates, airspace management platform 56 permits theflexibility to scan immediately (on-demand) or schedule a rogue AP scanfor a later time. Scheduling is a desirable feature as Rogue AP scansare obtrusive to the WLAN environment. Specifically, when a wirelessaccess point 52 is configured to scan in RF promiscuous mode, it onlylistens or monitors for wireless traffic, because, given the collisionavoidance mechanisms associated with the 802.11 protocols, transmittingdata may prevent any incoming traffic it was trying to collect. As oneskilled in the art will recognize, other wireless networking protocolsmay allow wireless access points to simultaneously operate in RFpromiscuous mode and access point mode. Accordingly, during a scan,wireless client devices 60 are disconnected from the scanning wirelessaccess point 52 and, therefore, have no connectivity to LAN 20.Scheduling Rogue AP scans at night or on the weekend reduces theopportunities that wireless client devices 60 experience a loss ofnetwork connectivity. As FIG. 5 illustrates, airspace managementplatform 56 also supports both serial and parallel methods of executingthe scan within a group as to both scheduled scans and on-demand scans.Serial scanning enables a well designed wireless LAN to maintainwireless client connectivity, because only a single wireless accesspoint 52 scans at any given time. When an access point is off-line forscanning, the wireless clients can immediately associate, without lossof connectivity, to an adjacent wireless access point 52, if any, withthe same SSID or within the same ESS (Extended Service Set).

After rogue AP scanning parameters are entered, airspace managementplatform 56, in one embodiment, builds a job schedule. In oneembodiment, all tasks are executed as jobs via the scheduler whether thejob is scheduled for a later time or immediate/on-demand. In oneembodiment, a task comprises a scan by a single wireless access point52; accordingly, a requested group scan may yield a plurality of jobs inthe job scheduler. In one embodiment, when the job scheduler executes ajob, it constructs an SNMP SET request and transmits it to the wirelessaccess point 52 associated with the job. For example, in embodimentswhere wireless access point(s) 52 support(s) the SNMP MIB set forth inAppendix A, the job scheduler executes a SNMP SET request for ObjectIdentifier (OID) (1.3.6.1.4.12028.4.3.4 BeginRogueAPScan) which, in oneembodiment, passes the following value sets: {(packetsToCollecttype-integer, value), (secsToWaitPerChan type-integer, value),(channelBeginScan, type-integer, value), (channelEndScan, type-integer,value), (channelToSkip, type-integer, value), and (numberoflterations,type-integer, value)} [see Appendix A]. In one embodiment, airspacemanagement platform 56 waits for a configurable number of seconds afterthe SNMP SET request to receive all device scan traps (scanDataRow) andthe end of scan trap (endRogueScan) from the scanning access point 52.If no traps are received, airspace management platform 56 transmitsanother SNMP SET request. If no traps are received after a thresholdnumber of SET requests, airspace management platform 56 reports a faultcondition to the network administrator.

B. Scanning Wireless Airspace

After receiving the SNMP-SET request from airspace management platform56, the wireless access point 52 invokes a locally executed scanningagent which moves its WLAN Network Interface Card (NIC) card from BSSmaster mode or normal AP mode, to a promiscuous RF monitoring mode. ManyWLAN network interface cards installed on currently available wirelessaccess points include promiscuous monitoring functionality, such asPrismII cards in LinkSys®, D-Link®, Compaq®, and Cisco® wireless accesspoints. Promiscuous monitoring mode is a process that has analogy on thewired or wire line medium. On a wired network most Ethernet cards filtertraffic so that only traffic destined for that card (installed in a PCor other network device) is received into higher layers of the operatingsystem. Placing the LAN NIC card into “promiscuous mode” causes the LANNIC to pass all traffic seen on the wire to higher layers in theoperating system. On a non-switched or hub network, a computer ornetwork device with its network card in promiscuous mode can listen toall traffic on the network segment. Similarly, in 802.11 or otherwireless networks, the WLAN NIC, operating in its normal mode, onlysends data packets destined for the device or management packets forBasic Service Set to higher layers in the operating system. In 802.11wireless networks, wireless NICs, operating in a normal mode, only sendpackets within the same BSS and the same SSID to higher layers of theoperating system. RF promiscuous mode, however, enables the wireless NICto sniff all traffic in the surrounding airspace (radio coverage areaand relative to one to a plurality of channels) regardless of networkassociation.

FIG. 6 illustrates a method, according to an embodiment of the presentinvention, directed to scanning for rogue access points. When adesignated wireless access point 52 receives an SNMP SET request (above)(102), a scanning agent changes the configuration of wireless accesspoint 52 to operate in promiscuous RF monitoring mode (104). Once inthis mode, the scanning agent executing within access point 52 uses thevariables passed within the SNMP SET request to OID “beginRogueScan” toexecute the properly formulated scan. Specifically, the scanning agentbegins listening on the channel defined in the “channelBeginScan”variable (106). The scanning agent monitors this channel for packets andanalyzes detected packets in order to build a memory array includingdata corresponding to detected wireless client devices and access points(114). In one embodiment, while a variety of packet types may bepresent, the scanning agent is configured to process only data packetsand management-beacon packets to build the memory array of wirelessdevices, as discussed below. As FIG. 6 illustrates, the scanning agentlistens on the current channel until it collects the number of packetsdefined in variable “packetsToCollect” (110) or until the channel timerhas expired defined in variable “secsToWaitPerChan” (112). Next thescanning agent proceeds to the next channel (current channel+SNMPvariable “channelToSkip”) (116) until the next channel is greater thanSNMP variable “channelEndScan” (108).

FIGS. 7A (management) and 7B (data) set forth the frame layout accordingto the 802.11 specification and illustrates how the scanning agentanalyzes the data packets gathered while in the promiscuous monitoringmode to populate a memory array. FIG. 7A illustrates the frame layout ofa management packet, such as a beacon packet transmitted by an accesspoint. As FIGS. 7A and 7B illustrate, packet type (e.g., data v. beacon)in the 802.11 standard can be determined by examining the values of theframe control bits. FIG. 7A illustrates how the scanning agent candetect various fields such as BSSID, SSID, Channel and the like.Furthermore, FIG. 7B illustrates the frame layouts of data packetstransmitted from (top layout) and to (bottom layout) a wireless accesspoint. As FIG. 7B illustrates, the direction of data packets can bedetermined by evaluation of the values of the frame control bits. Withthe direction, the scanning agent can resolve whether the first address(address 1) or the second address (address 2) corresponds to the accesspoint (BSSID). The RSSI (relative signal strength) is provided by aphysical layer header called PrismII monitor header that is not a partof 802.11 frame header, but is generated by the firmware of thereceiving card. One skilled in the art will recognize that otherwireless protocol standards feature different frame layouts and will beable to configure the scanning agent to parse the various data fields inthe packet or frame headers.

In addition, FIG. 8 illustrates a memory array (top table) includingdata obtained during a hypothetical scan for didactic purposes. Forexample, the first row of the memory array indicates that, on channel 1,the scanning access point detected a data packet transmitted from/to awireless client (see Type field) associated with an access point havinga WLAN MAC address or BSSID of 00:02:2D:03:4C:B0. Further, the secondrow indicates that the scanning access point also detected a data packetfrom the same client on channel 2. As one of skill in the art willrecognize, the channels defined in the 802.11 specification only include3 non-overlapping channels (1, 6 and 11) among the total number ofchannels. As one of skill in the art understands, the channel representsthe center frequency that the transceiver within the radio and accesspoint uses (e.g., 2.412 GHz for channel 1 and 2.417 GHz for channel 2).There is only 5 MHz separation between the center frequencies.Furthermore, an 802.11b signal occupies approximately 30 MHz of thefrequency spectrum. The signal falls within about 15 MHz of each side ofthe center frequency. As a result, an 802.11b signal overlaps withseveral adjacent channel frequencies. This leaves only three channels(channels 1, 6, and 11 for the U.S.) that can be used without causinginterference between access points. Accordingly, a scanning access pointis likely to detect data packets from a given wireless client or accesspoint on more than one channel. For example, scanning on channels 3 and4, the scanning access point 52, in the didactic hypothetical, detectedbeacon packets from an access point having a MAC address of00:02:2D:03:4C:B0 and configured with an SSID of “AirPort Network.” AsFIG. 8 shows, the scanning access point detected no wireless traffic onchannel 8 during the scan.

As FIG. 6 further illustrates, after the scan and memory arrayconstruction, the scanning agent analyzes the memory array (118) andsends back a summarized set of traps to airspace management platform 56(120). The table illustrated in FIG. 8 and entitled “Post Analysis DataSent via SNMP to AMP from Scanning AP” illustrates the scanDataRow traps(each row corresponding to a trap). In one embodiment, the scanningagent resolves discrepancies such as the channels on which packets weredetected in creating the scanDataRow traps. See also Appendix A(“scanDataRow”). As FIG. 8 illustrates, the scanning agent logicallyassigned the closest usable (non-overlapping) channel to the networksimplemented by access points “00:03:2F:00:12:AE” and“00:02:2D:0D:4D:7C”. Also notice the Access Point “00:02:2D:03:4C:B0” issummarized into a single trap event though it was heard on channel 3 andchannel 4. Because 802.11-compliant beacon frames identify thetransmitting channel, the scanning agent assumes that the channelidentified in the beacon packet (here, channel 1) is correct and thatthe data packet detected during the scan on channel 4 bleed-over fromchannel 1. In the example illustrated in FIG. 8, at the end of theanalysis, the scanning access point 52 would transmit to airspacemanagement platform 56 four “scanDataRow” SNMP traps and one“endRogueAP” SNMP traps (signaling the end of the scan and indicatingthe number of scanDataRow traps sent).

As one skilled in the art will recognize, the scanning agent describedabove does not distinguish between registered/authorized wirelessdevices and rogue or non-registered devices. Rather, as discussed above,the data generated during the scan is summarized and sent as SNMP trapsto airspace management platform 56, which processes the traps (asdiscussed more fully below) to detect the present of rogue access pointsand/or wireless clients. One skilled in the art will recognize, however,that this division of functionality is not required by any constraint,and that the scanning agent executed by the access point(s) 52 can beconfigured to detect for the presence of rogue access points andtransmit corresponding SNMP traps to airspace management platform 56. Apreferred embodiment, however, is the example described herein where thescanning agent running on the access point only collects datacharacterizing detected wireless traffic and transmits this collecteddata or summarized versions to airspace management platform 56 forfurther analysis. Airspace management platform 56, according to apreferred embodiment, performs the analysis of the data, functioning asthe SNMP manager while the access point functions as the agent inaccordance with the principal foundations of the SNMP framework.

B.1. Identification of Access Points from SNMP Trap Data

Airspace management platform 56 receives the scanDataRow traps andprocesses them to identify rogue wireless devices. In one embodiment,each scanDataRow trap is processed against the information contained inone to a plurality of tables to identify rogue wireless devicesoperating within the airspace associated with the wireless networkenvironment. In one embodiment, airspace management platform 56maintains three categories of wireless devices: 1) authorized, 2) rogue,and 3) ignored. Authorized wireless access points are generally businessgrade access points (e.g. manufactured by Cisco, Lucent, Symbol, etc.)that have been authorized by the enterprise/network administrator andregistered with airspace management platform 56 (see above). Asdiscussed above, information relating to authorized access points iscontained in the AP_Master table. As discussed more fully below,airspace management platform 56, in one embodiment, also maintains aRogue_Master table and an Ignored_Master table. An authorized wirelessclient or wireless station associates to an authorized access point andalso possesses valid authentication credentials granted by a centralsecurity system. Rogue wireless devices encompass any wireless device(client or access point) in the enterprise's airspace that is notregistered as an authorized or ignored device, as indexed by WLAN MACaddress in the appropriate tables within the airspace managementplatform 56. The ignored category represents wireless devices that havebeen processed through the rogue detection process set forth herein,reported to the network administrator and configured by theadministrator in the Ignored category. An example would be an accesspoint from a neighboring business. The access point is not rogue, but isnevertheless worthy of attention and is generally ignored until a changeassociated with the access point is detected.

Against this exemplary backdrop, each “scanDataRow” trap is processed inthe following manner. Airspace management platform 56, in oneembodiment, evaluates the “awAPReturnBSSID” against the three categoriesof wireless devices (authorized, ignored and rogue) in the Master,Ignored and Rogue AP tables. FIG. 9 sets forth a method for processingscanDataRow traps according to an embodiment of the present invention.In one embodiment, airspace management platform 56 first queries theAP_Master table, searching for matches between the awAPReturnBSSID andthe WLAN MACs of the AP records in that table (204). If there is amatch, airspace management platform 56 builds a history record for theAP (220), showing that it was scanned by the AP defined in the value“awAPScanID” or LAN MAC address.

If there is not a match between the “awAPReturnBSSID” and the WLAN MACsof the AP_Master table records, then airspace management platform 56determines whether the “awAPReturnBSSID” matches any records containedin the Rogue_Master (208) and Ignored_Master (206) tables. If theawAPReturnBSSID matches an entry in either table, airspace managementplatform 56 builds a history record for the matching access point asdiscussed above. If there is not a match in either the Rogue_Master orIgnoredMaster tables, then the airspace management platform 56 creates aRogue_Master record with an index using the WLAN MAC or“awAPReturnBSSID” (210). As FIG. 9 shows, airspace management platform56 also builds a history record for the Rogue AP (220), showing that itwas scanned by the AP defined in the value “awAPScanID” or the LAN MACaddress.

In one embodiment, history records are maintained in a history tableindexed by WLAN MAC address and further contain the remaining dataelements contained in the scanDataRow trap. By building theserelationships, airspace management platform 56 can analyze these historyrecords to determine which authorized access points are contiguous, onwhat channel these APs are broadcasting, and the relative signalstrength of their transmissions. Utilizing this information, airspacemanagement platform 56 can automatically configure (or the networkadministrator can manually configure) the transmission power level andchannel for optimum performance in light of the surrounding accesspoints. For 802.11b as regulated in the United States in particular,there are only 3 non-overlapping channels (1, 6, and 11), so thishigh-level logic is extremely valuable and can be used to ensure thatcontiguous access points (those with overlapping airspaces) areconfigured to broadcast on non-overlapping channels. In a multi-floorenvironment a third dimension of height or floor level is added.Airspace management 56 seamlessly learns and links all access points bycontiguous airspace by determining which access points can sense eachother. As discussed above, the AP_Master record also stores thepositional (e.g., GPS) coordinates associated with each wireless accesspoint 52, allowing a true 3-dimensional depiction of a WLAN environment.Currently produced access points do not generally contain GPS receivers,accordingly, the information recorded in the database is only asaccurate as a human translating the GPS reading from a handheld deviceat the location of the access point, and inputting the information intothe database of airspace management platform 56. As one skilled in theart will recognize, the integration of GPS receivers into wirelessnetwork access points and corresponding MIB extensions to expose the GPScoordinates computed by the receiver can be readily accomplished.Accordingly, future embodiments of airspace management platform 56 alsocontemplate querying access points via SNMP or similar protocols for GPScoordinates. Even without GPS coordinates, airspace management platform56 is still able to produce a 2-dimensional representation of theairspace associated with an administrative domain, mapping outcontiguous access points.

B.2. Notifications

In one embodiment, an aspect of airspace management platform 56 isoperative to provide notifications upon the detection of certain events(e.g., detection of a rogue access point, changes to ignored devices,changes/degradation of network performance characteristics, etc.). Alldata from access points, clients, security repositories, and networkinfrastructure is monitored on a real-time or near-real-time basis.Airspace management platform 56 further allows network administrators todefine triggers when one or more collected data values exceed athreshold. Triggers cause an alert action to take place when thethreshold is exceeded. Rogue access points, in one embodiment, fallunder the security category. In one embodiment, there is a specificsystem trigger entitled “New Rogue AP Discovered” where a networkadministrator can define how he/she wants to receive immediatecommunication about the presence of a rogue device in the airspace. Thethree avenues for communication, in one embodiment, are email (addressor distribution list), log (message is written into a syslog), and NMS(a trap is sent to a Network Management System like HP OpenView).

FIG. 9 illustrates that, in one embodiment, airspace management platform56 issues a notification in response to the detection of rogue accesspoints and/or changes to ignored access points. As described above,wireless devices discovered during a wireless scan of the airspace arecategorized depending on airspace management platform 56 system settings(e.g., the state of the AP_Master and other tables) as Authorized,Ignored or Rogue. Specifically, as FIG. 9 shows, when airspacemanagement platform 56 categorizes a wireless device as a rogue device(208,210), it issues a notification (216). Similarly, detected changesto an Ignored device (214) can also cause airspace management platform56 to issue a notification. In one embodiment, the ignored_Master tablecontains a flag “AlertOnChange”. If this flag is set (212), airspacemanagement platform 56, in one embodiment, compares the channel, SSID,and WEP of the Ignored access point in the Ignored Master Table to theinformation received in the scanDataRow trap.

The Ignored device category, in one embodiment, can be used for accesspoints that are not rogue access points connected to an enterprise'slocal area computer network, but for those access points thatnevertheless overlap with the airspace associated with the enterprise'sadministrative domain. For example, this could be a legitimate,physically-adjacent enterprise's access point beyond the networkadministrator's control, but still worthy of monitoring. For example,the network administrator having knowledge of such an access point canengineer his network so that the access points 52 that overlap theairspace with the neighboring access point are operating on a differentchannel and SSID. The “AlertOnChange” flag, in one embodiment, indicatesto airspace management platform 56 only to notify the networkadministrator when this Ignored device changes channel, SSID, orlocation, as these settings and the access point's location could impactthe performance of the enterprise's wireless network. When the“AlertOnChange” flag is set airspace management platform 56 looks at thetrigger definition of “Ignored AP Alert on Change” and sends theappropriate notifications. As one skilled in the art will recognize, thedetection of a new/unknown wireless device, according to the embodimentsdescribed above, will never directly create an entry into theIgnored_Master table. Rather, as FIG. 9 illustrates, the detection of anunknown wireless device creates a new entry into the Rogue_Master tableand is reported to a network administrator. The network administratorcan then decide whether to place the discovered wireless device in theIgnored category and, therefore, the Ignored_Master table.

In one embodiment, airspace management platform 56 allows networkadministrators to configure a “New Rogue AP Discovered” trigger defininghow notifications are issued. Depending on the definition of “New RogueAP Discovered” trigger, airspace management platform 56, in oneembodiment, creates a notification or notifications containing thefollowing information: 1) LAN MAC and AP Name of discovering accesspoint, 2) date and time the scan was initiated, 3) the duration of thescan, 4) the WLAN MAC of the Rogue device, 5) the SSID of the WLANdevice, 6) the channel of the Rogue device, and 7) potentially theClient Radio MAC address. Included in each of these notifications,according to one embodiment, are URL links back to the Rogue Event,Discovering access point, and Rogue device. The URL link enablesrecipient network administrators immediate access over a computernetwork to resolve the rogue problem. FIG. 11 illustrates a userinterface, according to an embodiment of the present invention,detailing the information characterizing a detected rogue access point.

C. Isolation of Rogue Access Points

Once the scan or scans are complete and all scanDataRow traps areprocessed, airspace management platform 56 is operative to displayinformation characterizing the state of the enterprise's airspace. FIG.10 shows a user interface displaying a list of rogue devices detectedduring a scan. This page allows WLAN administrators to view all Rogueaccess points discovered in the scan and take appropriate action withrespect to them. As FIG. 10 illustrates, airspace management platform56, in one embodiment, summarizes the rogue device information and sortsthem by discovered date and time. From this interface, a networkadministrator can identify the number of rogue devices in the airspacethat require further attention. In one embodiment, airspace managementplatform 56 includes an OUI database, which is an OrganizationallyUnique Identifier or a 24 bit globally unique assigned number from IEEE.This database allows airspace management platform 56 to match the firstthree octets of the Rogue WLAN MAC address back to the originalmanufacturer. In one embodiment, airspace management platform 56includes an extended OUI database that incorporates model numbers to the4^(th) and 5^(th) octets and cross referenced wireless manufacturer OUlsto their resale entities. As FIG. 10 shows, additional columns from thisview include AP Name, SSID, Channel, WEP, RSSI, Discovery Date and Time,and Discovery Agent or AP. As FIG. 10 shows, the AP Name is blank unlessand until the network administrator configures a name for it.

The SSID column allows the network administrator to quickly ensure thatthe detected rogue access point is not conflicting with a SSID of anauthorized access point within the airspace associated with theenterprise's wireless LAN as it could hijack legitimate users associatedwith the conflicting authorized access point. The channel field is selfexplanatory, but plays an additional role in the Rogue Detail View. TheWEP column allows an administrator to determine how large a securitybreach the access point really is. If WEP is disabled then the accesspoint could potentially be bridging the enterprise LAN to any personwithin the access point's radio coverage cell. The Relative SignalStrength (RSSI) column represents the signal strength identified fromthe discovering access point to the rogue device.

FIG. 11 sets forth a user interface providing a detailed view ofinformation relating to a given rogue access point detected during thescan. To continue the process of examining the rogue device, anadministrator may drill into the detail view by double clicking the MACor the AP Name in the interface of FIG. 10. If the AP Name is not knownit will display “Unknown”. The user interface provides a networkadministrator the opportunity to name the detected device. The table hasindexes on the WLAN MAC and the LAN MAC of the rogue device so duplicateor blank AP names do not breach the integrity of the database. In thedetail view the administrator has the ability to update the AP Name, GPScoordinates, and notes regarding the access point. The first pass atthis view can be utilized to find all access points that were detectedwithin the airspace(s) of the scanning access point(s) 52. Eitherutilizing GPS or basic triangulation a network administrator with theinformation provided by airspace management platform 56 has a goodestimate of the location of the rogue access point. The relative signalstrength indicator value adds some granularity to the potential locationof the device as a small RSSI value relative to one scanning accesspoint indicates that it may be further away, while a RSSI valueindicates that it may be closer to the scanning access point.

The administrator now can proceed to the approximate location of thedetected rogue access point with a GPS Receiver and wireless scanningtool. When the access point is located, the network administrator canphysically disable the access point (for access points located on thewired network), note location (for access points not connected to thewired network), or take any other appropriate action. Using the airspacemanagement platform 56, the network administrator can update as muchinformation gathered about the rogue access point by assigning a Nameand notes about whom and how the access point was installed. Forexample, the rogue device could be an access point from a neighboringbusiness. In this instance the name and notes fields would reflect thisinformation. After updating the data, the network administrator candelete the record corresponding to the rogue access point, leave it inthe rogue category, or place it in the authorized category (if roguedetection is being used to discover new and authorized devices) or theignored category. Ignoring or deleting the rogue device completes theisolation process work flow for the selected rogue device. Theadministrator can then continue working on analyzing the remainingdevices on the list until all rogue devices are isolated.

The following provides a didactic example illustrating application ofthe present invention. One example of this scenario would be where afirst business installs a wireless network at a remote facility.Subsequently, an adjacent entity decides to install a WLAN in its smalloffice. This access point is not a rogue as it is not installed on theenterprise's network, but the enterprise would nevertheless want to knowabout it. The first time a Rogue Scan is run on the access point forthat particular remote facility, the discovered access point associatedwith the adjacent business would be detected and Recorded as a roguedevice. The network administrator would be very interested indetermining whether the rogue device runs on the same or overlappingfrequency channels of authorized access points that detected the roguedevice during the scan. This would aid the administrator in adjustingthe configuration of, and optimizing the performance of, theenterprise's wireless network. The network administrator would also wantto ensure that the adjacent access point is not configured with the sameSSID. The network administrator may also desire to know whether WEP wasenabled on the adjacent access point as any wireless client mayassociate to the rogue access point that does not have WEP enabledinstead of the desired enterprise access point. Using airspacemanagement platform 56, the network administrator could quickly run areport to show usage patterns for the days preceding detection of therogue device. If the number of users and wireless traffic has declinedsignificantly, then the network administrator could travel to the remotelocation to determine the best means of resolution. If the user andtraffic numbers have not declined, the network administrator couldsimply move the detected access point to the ignored classification with“alert on change” set. As the example illustrates, the present inventionreduces the cost of monitoring the WLAN by (1) minimizing the time andresources required to roam throughout the enterprise with a laptopsniffing for rogue access points and users, by (2) allowing anenterprise to leverage a single device, or multiple devices, to functionas an access point and air scanner, and (3) by centrally managing allaccess points from a single console.

Another embodiment of this present invention, discloses a method andsystem for detecting all interfaces, LAN MAC addresses and radio MACaddresses (BSSIDs), affiliated with a rogue device operating in a hybridnetwork. Once detected, this information can be compiled into a databasein order to reduce the number of alerts that one rogue device cangenerate and to increase the accuracy and speed of locating the roguedevice within the network.

FIG. 12 a illustrate a flow chart diagram for a method according to anexemplary embodiment of the present invention. In particular, the methodis directed to the scanning for rogue devices (over-the-air andon-the-wire), gathering data of the detected rogue devices, analyzingthe data gathered, and building a master device record which relates allof interfaces detail records.

Initially, at step 1201, an access point (AP) scans its airspace andretrieves a list of BSSIDs from radios communicating within thereception range of the access point. This scanning occurs continuouslyto provide up-to-date information about neighboring wireless devices. Atstep 1202, an AirWave Management Platform (AMP) queries the AP via SNMPand to retrieve the list of BSSIDs detected by that access point.

Next at step 1203, the AMP creates a discovery event for all BSSIDsreturned from the access point. The discovery event will includeinformation relating to the detected device such as signal strength,BSSID, security and channel. Creating a discovery event for each BSSIDenables the AMP to map the RF environment and locate the particularrogue device via triangulation and/or other location methods.Subsequently, at step 1204, the AMP compares the detected BSSIDs to alist of BSSIDs (radios) currently under the AMP's management. If theBSSID is managed by the AMP, the AMP will recognize that the device isinherently not a rogue device, and, therefore, poses no security risk.Accordingly, the AMP reverts to step 1202. Alternatively, if the BSSIDis not managed by the AMP (i.e., it is not part of the existing list),then it is potentially a rogues device and a rogue discovery record(over-the-air) is therefore created (step 1205).

In one embodiment of the method, a score that indicates the level ofsecurity risk may be assigned to the BSSID by AMP at step 1206. Forexample, higher scores may indicate a greater security risk with “7”being the highest score that can be assigned to a rogue device. In oneembodiment, the score is preferably assigned to the BSSID using thefollowing scheme: (1) any MAC address on the wired network; (2) a MAC onthe wired network whose OUI belongs to a company that manufacturerswireless devices; (3) a MAC on the wired network whose OUI containsenterprise wireless access points; (4) a MAC on the wired network whoseOUI contains SOHO wireless access points; (5) a MAC on the wired networkthat has an associated IP and an embedded operating system (e.g.,VxWorkS™ or Linux™); (6) a BSSID or multiple BSSIDs that belongs to adevice that was only detected over-the-air; and (7) a rogue devicedetected over-the-air that is also on the monitored wired network. Itshould be understood that a rogue device that is not on the wirednetwork (security risk score of “6”) can cause interference problems,but a rogue device that is in the airspace and actually on the monitoredwired network (security risk score of “7”) may pose a significantlyhigher security risk since it potentially has access to a great deal ofsensitive data.

Referring back to FIG. 12 a, once the score is assigned to the BSSID,the AMP continuously evaluates all rogue discovery records searching fora root BSSID (step 1207). The root BSSID, also referred to as a“burned-in addresses” (BIA), is a unique address assigned to a device byits manufacturer. The first three octets identify the organization thatissued the identifier (i.e., the OUI) and the following three octets(MAC-48 and EUI-48) or five octets (EUI-64) are assigned by thatorganization in a discretionary manner. Generally, the root BSSID isstored in a very small EEPROM during final board assembly for thedevice.

If the AMP does not identify a new root BSSID from the rogue discoveryrecords at step 1207, then the AMP queries the AP or controller via SNMPagain in order to retrieve the updated list of BSSIDs as illustrated instep 1202. Alternatively, if a root BSSID is identified, the AMP createsa rogue device record and assigns the root BSSID from the roguediscovery record to the rogue device record (step 1208).

FIG. 12 b is a continuation of the flow chart in FIG. 12 a, whichfocuses on populating rogue interfaces related to the rogue devicerecord created at Step 1208. In particular, after the rogue devicerecord is created, the AMP creates a rogue interface record for the rootBSSID for the rogue device (step 1209). The AMP further analyzes alldiscovery events for virtual BSSIDs related to the root BSSID andcreates individual interfaces records indexed back to the rogue devicerecord (step 1210). In general, virtual BSSIDs are generated if the enduser programs the access point to have multiple networks. As such, thevirtual BSSIDs would be based on the root BSSID and be associated to thedifferent networks of the access point. Therefore, the rogue devicerecord generated at step 1210 would identify the root BSSID and furtherinclude a list of all related virtual BSSIDs that are based on the rootBSSID. One potential benefit of this feature is that the user isprevented from receiving numerous alerts, but rather receives a singlealert that would contain a list of all wireless interfaces (BSSIDs)along with wired interfaces, which will now be discussed.

Referring back to FIG. 12 b, the AMP searches for any wired MACaddresses associated with the root BSSID in the network (step 1211). Thesearch comprises reading the switches' bridge forwarding tables androuters' address resolution protocol (ARP) tables to find all of thewired devices on the network. It is noted that the ARP tables kept inthe network devices provide a means to map MAC addresses to IPaddresses. Once the search is complete, a rogue discovery event iscreated at step 1212 for all identified wired MAC addresses.

The AMP then analyzes all of the wired discovery events in step 1213 toverify whether any of the LAN MAC addresses match the first five octetsof the root BSSID of the rogue device record created in step 1208. Ifthere are no matches, the AMP continues to search for any wired MACaddresses as discussed in step 1211. Otherwise, if there are any matcheson the first five octets between the rogue device's root BSSID and theLAN MAC addresses in the rogue discovery event, then it is determined atstep 1214 whether there are multiple matches. If so, the closest matchto the root BSSIDs at step 1215. If there are not multiple matches, thenthe AMP creates a new rogue interface record bearing the closest of manyor the only LAN MAC address matching the first five octets of the roguedevice record's root BSSID (step 1216). It is noted that determining amatching for the first five octets is only one exemplary embodiment ofthe invention, however, the application is in no way intended to belimited to this embodiment.

Once this rogue interface record is created, the AMP sends a query tocheck if the rogue device contains an IP address (step 1217). If so, theAMP probes the IP address at step 1218 to determine if there are anyopen ports, which enables the determination of the operating system ofthe rogue device. As discussed above, a device running an embeddedoperating system like Linux™ or VxWorkS™ will be given a higher score(i.e., higher security risk assessment) than other non-embeddedoperating systems like MS Windows™, MS XP™, or MAC OS™.

At this point, all relevant information is compiled and indexed in adatabase. The information about each rogue device is displayed as acollection of many interfaces on a single screen in text or HTML (step1219) as demonstrated by FIG. 15, which will be discussed below. Bycombining all of the interfaces into a single rogue device record, AMPcan send a single alert that a particular rogue device has beendetected.

FIG. 13 illustrates an exemplary screen display of data retrieved fromthe detected rogue device and a database created after completinganalysis of the rogue device. The retrieved data may include informationsuch as the BSSID, channel information, presence of security featuresand signal strength of the device. As further shown in FIG. 13, thisinformation is stored in a database record. The database record includesthe BSSID, score assigned, Rogue Radio ID, AP ID, and radio index forthe device that detected the rogue device, as well as any other relatedinformation. As illustrated, the database record further stores wiredinformation.

FIG. 14 illustrates another screen display in accordance with anexemplary embodiment of the invention. As shown, the screen displayportrays the location of rogue devices discovered during activitiescorresponding to Step 1219 of the foregoing method. This user-friendlydisplay of the rogue device's location in a floor plan can assist ITpersonnel in physically locating the device. In addition, the screendisplay presents statistical information about the network as well asthe location of the rogue devices and the corresponding properties ofthese rogue devices.

FIG. 15 illustrates yet another exemplary screen display in accordancewith an embodiment of the invention. As shown, the screen displayportrays a list of all interfaces on a rogue device as described abovewith respect to Step 1219 of the foregoing method. In one embodiment, ifa user click on the icon labeled “View on Map”, the screen display asshown in FIG. 14 is launched. As mentioned above, this screen displayportrays the physical location of the particular rogue device.

Although the present invention has been described as operating inconnection with wireless devices communicating via the 802.11b protocol,the present invention is in no way intended to be limited by suchapplication. Rather, the present invention has application in a varietyof computer network environments employing any suitable wirelessphysical and link layer protocols, such as 802.11a, 802.11b, 802.11g,MAC layer protocols 802.11d 802.11e 802.11h and 802.11i, and Radio Bands2.4 GHz and 5 GHz. Further, although embodiments of the presentinvention have been described as operating in connection with SNMP, anysuitable protocols can be used. In addition, although embodiments of thepresent invention have been described as operating in connection with alocal area network, the present invention can be deployed across othercomputer networks, such as the Internet or other wide area networks.

Accordingly, the present invention has been described with reference tospecific embodiments. Other embodiments of the present invention will beapparent to one of ordinary skill in the art. It is, therefore, intendedthat the claims set forth below not be limited to the embodimentsdescribed above.

APPENDIX A-MIB //*********************************************************** * // MIBDefinition //* SNMP Set request from AMP to AP that support AW MIB forRogues //* (1.3.6.1.4.12028.4.3(awAPMIB).4(beginRogueScan Set Request)// *********************************************************** *beginRogueScan OBJECT IDENTIFIER ::={ awAPMIB 4} packetsToCollectOBJECT-TYPE SYNTAX Integer MAX-ACCESS read-write STATUS currentDESCRIPTION “The number of 802.11 packets to collect prior to movingchannels” ::= { beginRogueScan 1 } secsToWaitPerChan OBJECT-TYPESYNTAX Integer MAX-ACCESS read-write STATUS current DESCRIPTION “Thenumber of seconds to listen on each channel” ::= { beginRogueScan 2 }channelBeginScan OBJECT-TYPE SYNTAX Integer MAX-ACCESS read-writeSTATUS current DESCRIPTION “Starting Channel for scan” ::= {beginRogueScan 3 } channelEndScan OBJECT-TYPE SYNTAX IntegerMAX-ACCESS read-write STATUS current DESCRIPTION “Ending Channel forscan” ::= { beginRogueScan 4 } channelToSkip OBJECT-TYPE SYNTAX IntegerMAX-ACCESS read-write STATUS current DESCRIPTION The number of channelto skip for each scan. 5 would get 1,6,11 for 802.11b in US” ::= {beginRogueScan 5 } numberOfIterations SYNTAX IntegerMAX-ACCESS read-write STATUS current DESCRIPTION “The number ofiterations - meaning the AP would start @ channelBeginScan listening forpacketsToCollect or secsToWaitPerChan and loop until channelEndScan fornumberOfIterations iterations. The default value is 1,99 will cause theAP to full time scan until next beginRogueScan is received ” ::= {beginRogueScan 6 } //*********************************************************** * // RogueAP Data Traps generate by the AP and sent back to the AMP //* //*(1.3.6.1.4.12028.4.3(awAPMIB).5(per row of data found) //*********************************************************** * //--scanDataAP OBJECT IDENTIFIER ::={ awAPMIB 5 } awAPScanID OBJECT-TYPESYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION “TheLAN MAC Address of the AP Performing the SCAN” ::= { scanDataAP 2}awAPReturnBSSID OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-onlySTATUS current DESCRIPTION “The BSSID or Radio MAC of the Access Pointdiscovered. Only present on APs” ::= { scanDataAP 3 } awAPReturnSSIDOBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS currentDESCRIPTION “The SSID of the Access Point discovered.” ::= { scanDataAP4 } awAPReturnChannel OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-onlySTATUS current DESCRIPTION “The Channel contained only in BeaconPackets. Program could guess by data packets collected on Channels 5,6,& 7 one could surmise that the client is on channel 6.” ::= { scanDataAP5 } awAPReturnWEPOn OBJECT-TYPE SYNTAX INTEGER {(1) False, (2) True]MAX-ACCESS read-only STATUS current DESCRIPTION “1 indicates WEP is & 2indicates WEP is on” ::={ scanDataAP 6 } awAPRetumType OBJECT-TYPESYNTAX INTEGER {(1) AP,(2) Client,(3) Adhoc, (4) Bridge }MAX-ACCESS read-only STATUS current DESCRIPTION “Type of device pickedup on scan” ::={ scanDataAP 7} awAPReturnRSSI OBJECT-TYPE SYNTAX INTEGERMAX-ACCESS read-only STATUS current DESCRIPTION “Relative SignalStrength” ::- { scanDataAP 8 ] awAPReturnClMAC OBJECT-TYPESYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION “MACaddress of client wireless NIC - only valid for client devices.” ::= {scanDataAP 9 } scanDataRow NOTIFICATION-TYPE OBJECTS { awAPScanId,awAPReturnBSSID, awAPReturnSSID, awAPReturnChannel, awAPReturnWepOn,awAPReturnType, awAPReturnRSSI awAPReturnClMAC} STATUS currentDESCRIPTION “This trap is sent for AP and client observed in the BSA.”::= { scanDataAP 1} //*********************************************************** * // * SNMPtrap from AP to AMP // * (1.3.6.1.4.12028.4.3(awAPMIB).6(endRogueScanSet Request) //*********************************************************** * //endRogueScan OBJECT IDENTIFIER::- { awAPMIB 6 ] awAPScanDurationOBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS currentDESCRIPTION “Total duration of scan in seconds” ::= { endRogueDuration 2} awAPTotTraps OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-onlySTATUS current DESCRIPTION “Total traps(devices) sent to the AMP” ::= {endRogueDuration 3 } endRogueScan NOTIFICATION-TYPE OBJECTS {awAPScanId, awAPScanDuration, awAPScanTotTraps] STATUS currentDESCRIPTION “This trap is sent for AP and client observed in the BSA.”::= { endRogueScan 1}

1. A method of identifying Media Access Control addresses of roguedevices operating in a hybrid network, the method comprising:identifying Basic Service Set Identifiers for devices operating on awireless network; creating a rogue discovery event for at least one ofthe Basic Service Set Identifiers of a device not authorized to operatein the hybrid network; determining a root Basic Service Set Identifierfrom the rogue discovery event; assigning the root Basic Service SetIdentifier to a rogue device record; searching the hybrid network forwired devices associated with the root Basic Service Set Identifier anddetermining corresponding Media Access Control addresses for the locatedwired devices; and comparing the Media Access Control addresses with aplurality of octets of the root Basic Service Set Identifier in therogue device record.
 2. The method of claim 1, further comprisingassigning a score to the rogue discovery event based on security risk.3. The method of claim 1, further comprising comparing the identifiedBasic Service Set Identifiers with a list of Basic Service SetIdentifiers of devices controlled by a management platform to determinewhether the corresponding device is authorized to operate in the hybridnetwork.
 4. The method of claim 1, further comprising mapping a radiofrequency environment from the rogue discovery event.
 5. The method ofclaim 1, further comprises locating each of the devices operating on thewireless network via a triangulation method.
 6. The method of claim 1,further comprising determining channel information from the roguediscovery event.
 7. The method of claim 1, further comprisingdetermining security information from the rogue discovery event.
 8. Themethod of claim 1, further comprising determining signal strength fromthe rogue discovery event.
 9. The method of claim 1, wherein thecomparing step further comprises identifying a device having the closestaddress when more than one Media Access Control addresses match the rootBasic Service Set Identifier in the rogue device record.
 10. The methodof claim 1, further comprising analyzing all rogue discovery events forthe at least one of the Basic Service Set Identifiers to determine avirtual Basic Service Set Identifier.
 11. The method of claim 10,further comprising creating a rogue interface record for the virtualBasic Service Set Identifier.
 12. The method of claim 1, furthercomprising creating a rogue interface record for the root Basic ServiceSet Identifier.
 13. The method of claim 1, wherein the comparing stepfurther comprises comparing the Media Access Control addresses with afirst five octets of the root Basic Service Set Identifier in the roguedevice record.
 14. The method of claim 1, further comprising creatingadditional rogue interface records for each of the Media Access Controladdresses that correspond to the first five octets of the root BasicService Set Identifier.
 15. The method of claim 14, further comprisingsearching the additional rogue interface records for the Media AccessControl addresses having corresponding Internet Protocol addresses. 16.The method of claim 15, further comprising querying at least one of theInternet Protocol addresses to determine an operating system of thecorresponding rogue device.
 17. The method of claim 1, wherein thesearching step further comprises reading bridge forwarding tables on aswitch to find the wired devices.
 18. The method of claim 1, wherein thesearching step further comprises reading address resolution protocoltables of a router to find the wired devices.
 19. A system forperforming a computer-based method of identifying Media Access Controladdresses of rogue devices operating in a hybrid network, comprising: acomputer having a memory and a processor; and a computer-readable mediumconfigured to generate software code, which, when said code is loadedinto the memory and run by the processor, causes the processor toperform the steps of: identifying Basic Service Set Identifiers fordevices operating on a wireless network; creating a rogue discoveryevent for at least one of the Basic Service Set Identifiers of a devicenot authorized to operate in the hybrid network; determining a rootBasic Service Set Identifier from the rogue discovery event; assigningthe root Basic Service Set Identifier to a rogue device record;searching the hybrid network for wired devices associated with the rootBasic Service Set Identifier and determining corresponding Media AccessControl addresses for the located wired devices; and comparing the MediaAccess Control addresses with a plurality of octets of the root BasicService Set Identifier in the rogue device record.
 20. A system forperforming a computer-based method of identifying Media Access Controladdresses of rogue devices operating in a hybrid network, comprising: acomputer having a memory and a processor; and a computer-readable mediumconfigured to generate software code, which, when said code is loadedinto the memory and run by the processor, causes the processor toperform the steps of: identifying Basic Service Set Identifiers fordevices operating on a wireless network; creating a rogue discoveryevent for at least one of the Basic Service Set Identifiers of a devicenot authorized to operate in the hybrid network; determining a rootBasic Service Set Identifier from the rogue discovery event; assigningthe root Basic Service Set Identifier to a rogue device record;assigning a score to the rogue discovery event based on security risk;searching the rogue discovery event to determine a virtual Basic ServiceSet Identifier; searching the hybrid network for wired devicesassociated with the root Basic Service Set Identifier and determiningcorresponding Media Access Control addresses for the located wireddevices; comparing the Media Access Control addresses with a first fiveoctet of the root Basic Service Set Identifier in the rogue devicerecord; creating a rogue interface record for the virtual Basic ServiceSet Identifier, the root Basic Service Set Identifier and for MediaAccess Control addresses that correspond to the first five octets of theroot Basic Service Set Identifier; searching the additional rogueinterface records for the Media Access Control addresses having InternetProtocol addresses; and displaying a location of at least one roguedevice.